How to handle bidirectional functionalities using links in the doors
|
Re: Bidorectional functionalities in doors Given a requirement, the test-writers will usually start an outlink on a test protocol that links to some requirement to be tested. People usually link this way because test-writers usually do not have write-permission to requirements documents. The only way for the test-writes to save the link(s) is in the test protocol document. The same applies for linking design document to requirements documents. |
Re: Bidorectional functionalities in doors yes, DOORS links are directional meaning they are associated with a start 'source' object and an ending 'target' object. Its best to set up links in link modules such that you can assign a meaningful verb to the link itself, e.g. "Requiement sub-1 'Satisfies' requirement Sys-2" or "Procedure abc_3 'Tests' requirements sub-1". Looking at the link from the target to the source will produce some other verb, perhaps 'justifies' or 'is tested by'. The name of the link module determines what that verb is. If you want to show a relationship between two objects but cannot come up with a verb to describe the relationship, you need to do more soul searching about your schema. There would be little reason to have two links between two objects in opposite directions; but I suppose if you had 'reference' links it might make sense, where "Requirements sub-1 'Refers To' Requirements Sys-2" but also "Requirment Sys-2 'Refers To' Requirments Sub-1".
|